home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Cream of the Crop 20
/
Cream of the Crop 20 (Terry Blount) (1996).iso
/
utility
/
ccache11.zip
/
CONCACHE.TXT
< prev
next >
Wrap
Text File
|
1996-06-22
|
28KB
|
768 lines
CONCACHE.EXE COPYRIGHT 1995-1996 horio shoichi CONCACHE.EXE
NAME
concache.exe - DOS concurrent disk cache
SYNOPSIS
concache [memory-arguments] [drive-arguments] [option]
[flags]
device=concache.exe [memory-arguments] [drive-arguments]
[option] [flags]
concache VECTOR [interrupt-number interrupt-id]
COMMAND LINE RULES
Command line has following rules
- Operands consist of options and terminating ';' (semi-
colon). Except for ';' , the order is unimportant.
- The character ';' (semicolon) terminates command line.
Operands after the character are ignored.
- All operands are case sensitive, and generally must be
in lower case. In this version VECTOR is the only
upper case operand. On config.sys line, operands are
converted to lower case and then interpreted.
- The character '/' can be placed anywhere ' ' (the white
space) can be placed.
- Alphabetic part of an option can be abbreviated down to
one character, if there is no ambiguities. For example
the delete option has the syntax [d[e[l[e[t[e]]]]]].
- Where drives are written, the character ':' (colon) can
be written, if adjacent to drive letter, as many as
wanted. For example, in concache.exe command line,
"sfg" is equivalent to "s:f:g:", "sf:g::", and so on.
The bitmap_length= and buffer_size= options and
gang_interrupts and gnaw_interrupt options are the only
those that at least leading two letters disambiguate.
DESCRIPTION
Conc286.exe has the same functionality with concache.exe
except that it runs also on 286 based compatibles with obvi-
ous limitation it is loaded only below 640kb of main memory
when under 286 CPU.
The concache.exe is the disk cache program for DOS environ-
ments. The other programs ccdisk.exe and floppies.exe works
Concache 1.10 Last Update: 20 June 1996 1
CONCACHE.EXE COPYRIGHT 1995-1996 horio shoichi CONCACHE.EXE
under the control of this program.
It is possible to load concache.exe into UMB (upper memory
block) by appropriate load command, such as devicehigh=
instead of device= or using loadhigh command. Also, it
loads its resident part into UMB with its option. This can
be convenient since this method is not affected by initial
concache.exe program size. See below for more.
After loaded as a character device driver or as a TSR (Ter-
minate and Stay Resident) program, concache.exe can change
most of parameters from command.com command line.
If used without any operand, concache.exe lists the flags in
effect, state of memory, and state of disks in use. con-
cache.exe gets this information from resident concache.exe
program.
After concache.exe has become resident, if windows is
started, concache.exe is expected to be readable from the
same drive and directory as it is loaded. For example, if it
is loaded from a floppy drive, the floppy media is refer-
enced at the same drive when windows starts.
Memory Arguments
These arguments determines the cache data area and their
sizes to be used for keeping copies of disk data. At least
one of them must be present for concache.exe to go resident.
Each of the named memories are examined and if enough memory
is available to satisfy the argument then they are used for
cache data area. Memory argument takes following forms
x[size]
Allocate/redefine extended memory according to XMS
(Extended Memory Specification) 2.0.
e[size]
Allocate/redefine expanded memory according to EMS
(Expanded Memory Specification) 4.0. Concache.exe does
not use page frames.
p[size]
Allocate raw protected memory, retrievable via BIOS
int15.
where size is the size to start or to continue concache.exe.
If size is not given, concache.exe uses all of available
memory of the type.
Concache 1.10 Last Update: 20 June 1996 2
CONCACHE.EXE COPYRIGHT 1995-1996 horio shoichi CONCACHE.EXE
Int15 memory is not allowed to change its size after once
concache.exe is loaded. Changing its size is only possible
by unloading and reloading concache.exe.
Extended and expanded memory can be changed at any time
after concache.exe is loaded. However, this must not be
exercised frequently, since this causes voiding accumulated
cached data in memory.
Size is written in decimal or in 0x preceded hexadecimal
value optionally followed by no space intervening m, mb, k,
kb, or b for megabytes, kilobytes, or bytes, respectively.
(A trailing b is for "bytes". If the hexadecimal is fol-
lowed by 'b' then it is interpreted as part of value but not
to mean "bytes".) The size is truncated to nearest multiple
of 64 kb. If total usable memory is less than 128 kb,
caching is not done.
The total maximum value concache.exe handles is 64 mb.
Drive Arguments
Drive arguments define cache refreshment policy for each
drive. They take the forms
c[drives] (default)
to refresh cache using concurrent method, that is, con-
cache.exe refreshes unwritten (wet) cache data back to
drives concurrently with user programs and DOS, and
possibly with the other devices,
a[drives]
to refresh cache not using concurrent method but using
write after,
w[drives]
to refresh cache with "write through" method. This is
the safest traditional disk cache method,
s[drives]
not to cache the data for the drives.
Drives are written after each c, a, w, s letter with no
spaces and tabs. Range expressions of drives are allowed.
For example, wja-df-h is equivalent to wabcdfghj to mean
drives a:, b:, c:, d:, f:, g:, h:, j: are to be cached with
write through method but drives e:, i:, and those after j:
are not.
It makes no sense to specify different refreshment policies
Concache 1.10 Last Update: 20 June 1996 3
CONCACHE.EXE COPYRIGHT 1995-1996 horio shoichi CONCACHE.EXE
for drives on the same devices. In these cases concache.exe
uses the most pessimistic policy for the drive. Note actu-
ally this happens only between concurrent and write after
methods.
If no drives are specified after any of c, a, w, s letter,
then it means "all the other" drives. For example aabc w
specifies drives a:, b:, c: are cached with write after
method but all the other drives are write through.
With similar syntax, following cache controls are available.
r[drives]
means refresh unwritten cache data back immediately.
The command awaits the completion of the writes.
f[drives]
means discard all data for the drive unconditionally,
written back or not. In practice, flush is seldom
used. If however, for example, floppy change line does
not work, then cached data for the device may have to
be flushed with this method.
n[drives]
disallows prereading on the drives. Normally con-
cache.exe schedules one block preread after a read
request is completed.
o[drives]
reenables prereading on the drives disabled by
n[drives].
The r[drives] and f[drives] are only meaningful after con-
cache.e